Conversation
|
✅ Commit pushed: |
|
|
||
| ### Changed | ||
| * Update FCS to 43.10.100. [#935](https://github.com/fsprojects/FSharp.Formatting/pull/966) | ||
| * Update FCS to 43.10.100. [#966](https://github.com/fsprojects/FSharp.Formatting/pull/966) |
There was a problem hiding this comment.
Could go for minor/major if we bump FCS, not a revision.
dsyme
force-pushed
the
repo-assist/release-v21.0.1-94aac80bb24352d6
branch
from
aefee2c to
3bd6c56
Compare
|
/repo-assist update this PR with latest changes and major version bump |
|
🤖 This is an automated response from Repo Assist. Hi # Changelog
## [Unreleased]
## 22.0.0 - 2026-02-24
### Added
* Add `(FsDocsAllowExecutableProject)true(/FsDocsAllowExecutableProject)` project file setting to include executable projects (OutputType=Exe/WinExe) in API documentation generation. [#918](https://github.com/fsprojects/FSharp.Formatting/issues/918)
* Add `\{\{fsdocs-logo-alt}}` substitution (configurable via `(FsDocsLogoAlt)` MSBuild property, defaults to `Logo`) for accessible alt text on the header logo image. [#626](https://github.com/fsprojects/FSharp.Formatting/issues/626)
### Fixed
* Improve error message when a named code snippet is not found (e.g. `(*** include:name ***)` with undefined name now reports the missing name clearly). [#982](https://github.com/fsprojects/FSharp.Formatting/pull/982)
* HTML-encode XML doc text nodes and unresolved `(see cref)` values to prevent HTML injection and fix broken output when docs contain characters like `<`, `>`, or backticks in generic type notation. [#748](https://github.com/fsprojects/FSharp.Formatting/issues/748)
* Add uppercase output kind extension (e.g. `HTML`, `IPYNB`) to `ConditionalDefines` so that `#if HTML` and `(*** condition: HTML ***)` work alongside their lowercase variants. [#693](https://github.com/fsprojects/FSharp.Formatting/issues/693)
* Strip `#if SYMBOL` / `#endif // SYMBOL` marker lines from `LiterateCode` source before syntax-highlighting so they do not appear in formatted output. [#693](https://github.com/fsprojects/FSharp.Formatting/issues/693)
### Changed
* Update FCS to 43.10.100. [#935](https://github.com/fsprojects/FSharp.Formatting/pull/966)
## 21.0.0 - 2025-11-12
...The changes vs the current PR branch:
Let me correct that — looking at the current Recommended action: Either update this PR branch directly using: git checkout repo-assist/release-v21.0.1-94aac80bb24352d6
git reset --hard origin/main
# Edit RELEASE_NOTES.md: change [Unreleased] → 22.0.0 - 2026-02-24
git commit -am "Release 22.0.0"
git push --force-with-lease origin repo-assist/release-v21.0.1-94aac80bb24352d6Or simply update
|
|
|
||
| ### Fixed | ||
| * Improve error message when a named code snippet is not found (e.g. `(*** include:name ***)` with undefined name now reports the missing name clearly). [#982](https://github.com/fsprojects/FSharp.Formatting/pull/982) | ||
| ## 21.0.1 - 2026-02-22 |
There was a problem hiding this comment.
/repo-assist bump to minor as we updated FCS.
2 participants
🤖 This is an automated PR from Repo Assist, an AI assistant for this repository.
Summary
This PR prepares the 21.0.1 patch release by updating
RELEASE_NOTES.mdto promote the[Unreleased]content to a versioned release entry.Changes Included
mainafter the 21.0.0 stable release.This keeps FSharp.Formatting aligned with the latest F# Compiler Services release.
What This Does
Changing the
## [Unreleased]header to## 21.0.1 - 2026-02-22inRELEASE_NOTES.mdcauses the CI pipeline (push-main.yml) to publish the new NuGet package version when merged.A fresh empty
## [Unreleased]section is retained at the top for future changes.Test Status